From: squirrel@echelon.alias.net (The Tech Lion)
Subject: FZ BIBLE - LEVEL 3 COURSEPACK [6/7]
Date: 14 Nov 1999 00:00:00 GMT
Message-ID: <3ed8d81610325a6e83010d5392896798@anonymous.poster>
Sender: Secret Squirrel <squirrel@echelon.alias.net>
Organization: FreeZone Bible Association
Mail-To-News-Contact: postmaster@nym.alias.net
Comments: Please report problems with this automated remailing service to <squirrel-admin@echelon.alias.net>. The message sender's identity is unknown, unlogged, and not replyable.
Newsgroups: alt.religion.scientology,alt.clearing.technology

FREEZONE BIBLE ASSOCIATION TECH POST

ACADEMY LEVEL III COURSEPACK: Part 6 of 7

***************************************

Continuing our quest to spread the Tech on the internet,
we bring you the Academy Level 3 coursepack from the late
1980s, in 7 parts.

The full table of contents is in Part 1 only.

To see the proper formatting, use a fixed-pitch font such as
Courier to view this file.

Looking forward to a Tech-filled Millenium,

-The Tech Lion 

********************

STATEMENT OF PURPOSE 

Our purpose is to promote religious freedom and the Scientology
Religion by spreading the Scientology Tech across the internet.

The Cof$ abusively suppresses the practice and use of
Scientology Tech by FreeZone Scientologists.  It misuses the
copyright laws as part of its suppression of religious freedom.

They think that all freezoners are "squirrels" who should be
stamped out as heretics.  By their standards, all Christians, 
Moslems, Mormons, and even non-Hassidic Jews would be considered
to be squirrels of the Jewish Religion.

The writings of LRH form our Old Testament just as the writings
of Judaism form the Old Testament of Christianity.

We might not be good and obedient Scientologists according
to the definitions of the Cof$ whom we are in protest against.

But even though the Christians are not good and obedient Jews,
the rules of religious freedom allow them to have their old 
testament regardless of any Jewish opinion.  

We ask for the same rights, namely to practice our religion
as we see fit and to have access to our holy scriptures
without fear of the Cof$ copyright terrorists.

We ask for others to help in our fight.  Even if you do
not believe in Scientology or the Scientology Tech, we hope
that you do believe in religious freedom and will choose
to aid us for that reason.

Thank You,

The FZ Bible Association

************************

PART 6

23. HCOB   19 Mar. 1971       List 1C--L1C

24. HCOB   23 July 1980R      Confessional Repair List--LCRE

25. HCOB   22 Aug. 1966       Floating Needles, Listing Processes

26. HCOB    1 Aug. 1968       The Laws of Listing and Nulling

27. HCOB   19 Sept 1968       "Old lists..."

28. HCOB    7 Oct. 1968       Assessment

29. HCOB   20 Sept 1978       An Instant F/N is a Read

30. HCOB   22 Apr. 1980R      Assessment Drills [encore]

31. HCOB   20 Apr. 1972 II    Product Purpose and Why and W/C
                              Error Correction
                              C/S Series 78

32. HCOB   11 Apr. 1977       List Errors, Correction of

33. HCOB   15 Dec. 68RA       L4BRA, for Assessment of All Listing
                              Errors

34. HCOB    6 Aug. 1968       R3H


******************************************************************

23. HCOB   19 Mar. 1971       List 1C--L1C


      HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

      HCO BULLETIN OF 19 MARCH 1971

Remimeo

             LIST 1C--L1C

       (Cancels earlier L1 Lists
        such as HCOB 8 Aug. 70)


Used by auditors in session when an upset occurs, or as ordered 
by C/S.

Handles ARC broken, sad, hopeless or nattery pcs.

Questions can be prefaced with "Recently" "In this life" "On the 
whole track" or used without.

DO NOT USE ON HIGH TA TO BRING IT DOWN. USE HI-LO TA LIST.

TAKE ALL READING ITEMS OR VOLUNTEERED ANSWERS earlier-similar to 
F/N as they occur.


1. Has there been an error in listing? (If this reads change to 
L4B at once.)

2. Has a withhold been missed?

3. Has some emotion been rejected?

4. Has some affinity been rejected?

5. Has a reality been refused?

6. Has a communication been cut short?

7. Has a communication been ignored?

8. Has an earlier rejection of emotion been restimulated?

9. Has an earlier rejection of affinity been restimulated?

10. Has an earlier refusal of reality been restimulated?

11. Has an earlier ignored communication been restimulated?

12. Has something been misunderstood?

13. Has someone been misunderstood?

14. Has an earlier misunderstanding been restimulated?

15. Has some data been confusing?

16. Has there been a command you haven't understood?

17. Has there been some word you haven't known the meaning of?

18. Has there been some situation you haven't grasped?

19. Has there been a problem?

20. Has a wrong reason for an upset been given?

21. Has a similar incident occurred before?

22. Has something been done other than what was said?

23. Has a goal been disappointed?

24. Has some help been rejected?

25. Has a decision been made?

26. Has an engram been restimulated?

27. Has an earlier incident been restimulated?

28. Has there been a sudden shift of attention?

29. Has something startled you?

30. Has a perception been prevented?

31. Has a willingness not been acknowledged?

32. Has there been no auditing?

33. Did you go exterior?

34. Have actions been interrupted?

35. Have actions continued too long?

36. Has data been invalidated?

37. Has someone evaluated?

38. Has something been overrun?

39. Has an action been unnecessary?


L. RON HUBBARD
Founder

LRH:mes.rd.gm



******************************************************************

24. HCOB   23 July 1980R      Confessional Repair List--LCRE


      HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

      HCO BULLETIN OF 23 JULY 1980R
          REVISED 26 JULY 1986

Remimeo
C/Ses
Auditors,
  Class II
  and above


      CONFESSIONAL REPAIR LIST--LCRE


  This HCOB cancels and replaces all of the following:

  HCOB 30 July 70    CONFESSIONAL REPAIR LIST L-CR
  HCOB  8 Dec. 72    INTEGRITY PROCESSING REPAIR LIST L1R
  HCOB  8 Dec. 72R   INTEGRITY PROCESSING REPAIR LIST
     Rev. 12.2.73    L1R
  BTB   8 Dec. 72R   INTEGRITY PROCESSING REPAIR LIST L1R
  BTB   8 Dec. 72RA  INTEGRITY PROCESSING AND O/Ws
                     REPAIR LIST-L1RA
  BTB   8 Dec. 72RB  CONFESSIONAL REPAIR LIST LCRB
  BTB   8 Dec. 72RC  CONFESSIONAL REPAIR LIST LCRC
  HCOB 20 July 80    CONFESSIONAL REPAIR LIST LCRD


This is the prepared list to use for repairing a Confessional, 
whether done as auditing or as an HCO Confessional. It is also 
for use in handling BPC from other O/W actions such as O/W
write-ups.

If, after a Confessional or O/W write-up, the person red tags at 
the Examiner or if he gets sick or upset or falls on his head, 
this list is assessed and handled to straighten the matter out. 
The repair action would be a 24-hour repair priority.

If there is a bog during a Confessional action, the auditor would 
first check for missed withholds, false reads and ARC breaks, in 
that order, and handle what he found. (Ref: HCOB 30 Nov. 78R, 
CONFESSIONAL PROCEDURE) If this does not resolve the difficulty, 
one should use the LCRE.

The list is usually assessed Method 3, but may be assessed Method 
5 in the case of a severe pc upset or as directed by the C/S.

The list should be used with a prefix which acts as a time 
limiter, such as "In this session, ______?" or "On your O/W 
write-up, ______?"


PRECLEAR:___________________________________ DATE:________________

AUDITOR:____________________________________


1. OUT-INT?                                               ________
(If you get a valid read, not a false or protest 
read, indicate it. If the pc has had an Int RD or
End of Endless Int RD previously, assess and handle
the Int RD Correction List. If the pc has not had 
previous Int handling or if the Int RD Correction 
List does not fully resolve the situation, do an Int 
RD or, on a Clear or OT, the End of Endless Int RD. 
If you are not qualified to deliver the Int RD or
the End of Endless Int RD, end off for a qualified 
auditor to handle.)

2. LIST ERROR?                                            ________
(Indicate. If Class III or above, find out what list 
and repair with L4BRA. If not Class III, end off for 
handling by a Class III or above.)

3. WRONG ITEM?                                            ________
(Handle as in #2.)

4. WAS THERE AN ARC BREAK?                                ________
(ARCU, CDEINR E/S to F/N.)

5. WAS THERE A PROBLEM?                                   ________
(2WC E/S to F/N.)

6. WAS A WITHHOLD MISSED?                                 ________
(Pull it getting who nearly found out, etc.
E/S to F/N.)

7. DID YOU TELL PART OF A WITHHOLD BUT NOT THE REST?      ________
(Get all of the withhold, flatten it E/S to F/N.)

8. DID YOU MISDIRECT THE AUDITOR?                         ________
(Handle as an overt, E/S to F/N. Flatten any
unflat Confessional chain uncovered.)

9. DID YOU AVOID TELLING ONE OVERT BY GIVING A
   DIFFERENT ONE?                                         ________
(Pull the overt the pc avoided telling, E/S to F/N.)

10. WERE YOU WAITING FOR A MORE SPECIFICALLY
    WORDED QUESTION?                                      ________
(Find out what Sec Check question the pc was waiting
for and get it answered, to F/N.)

11. DID THE AUDITOR FAIL TO FIND OUT SOMETHING
    ABOUT YOU?                                            ________
(Handle as a missed withhold, E/S to F/N.)

12. DID YOU FAIL TO ANSWER A SEC CHECK QUESTION?          ________
(Find out which question and handle to F/N.)

13. DID YOU DELIBERATELY NOT ANSWER A SEC CHECK
    QUESTION?                                             ________
(Find out what question and handle to F/N.)

14. DID YOU WITHHOLD SAYING SOMETHING FOR FEAR
    OF GETTING INTO ETHICS TROUBLE?                       ________
(Handle to F/N as per Sec Checking procedure.)

15. DID YOU TRY TO LESSEN AN OVERT?                       ________
(Find out how he tried to lessen the overt and
complete its handling to F/N.)

16. HAS AN OVERT BEEN JUSTIFIED?                          ________
(Pull the justifications off the overt, then
complete to F/N.)

17. WAS THERE SOME OTHER WAY YOU JUSTIFIED THE
    OVERT?                                                ________
(Pull the justifications off the overt, then
complete its handling to F/N.)

18. WORRIED ABOUT REPUTATION?                             ________
(Clean it up with 2WC E/S to F/N.)

19. ARE THERE OPINIONS YOU DON'T DARE SAY?                ________
(2WC E/S to F/N.)

20. WAS THERE AN EARLIER OVERT UNDISCLOSED?               ________
(Pull it E/S to F/N.)

21. WAS A CHAIN OF OVERTS NOT TAKEN BACK TO BASIC?        ________
(Take it back to basic.)

22. WAS AN OVERT TOO LATE ON THE CHAIN?                   ________
(Get the earlier overt and take the chain to F/N.)

23. JUMPED TO A DIFFERENT OVERT CHAIN?                    ________
(Reorient to the original chain and take it to F/N.
Then flatten the chain the pc jumped to, if reading.)

24. ARE YOU WITHHOLDING ANYTHING?                         ________
(Get what it is, E/S to F/N.)

25. DID YOU TELL A HALF-TRUTH?                            ________
(Get all of the withhold, handle E/S to F/N.)

26. WAS THERE SOMETHING THE AUDITOR SHOULD HAVE
    KNOWN ABOUT YOU THAT HE DIDN'T?                       ________
(Get what. Pull it E/S to F/N.)

27. WAS THERE AN UNDISCLOSED OUT-ETHICS SITUATION?        ________
(Get it off as a missed W/H, E/S to F/N.)

28. HAS A CRIME BEEN COVERED UP?                          ________
(Pull it, E/S to F/N.)

29. WAS THERE MORE THAT SHOULD HAVE BEEN KNOWN
    ABOUT SOME OVERT?                                     ________
(Get it all, E/S to F/N.)

30. WAS THERE A QUESTION THAT THE AUDITOR SAID DIDN'T
    READ THAT SHOULD HAVE?                                ________
(Find out what question and get in Suppress and Inval
on it. Then handle it to F/N.)

31. DID THE AUDITOR CALL AN F/N WHEN YOU DIDN'T
    FEEL YOU WERE F/Ning?                                 ________
(Find the point and get in Suppress on it, and
complete the action to F/N.)

32. DID YOU TELL A LIE?                                   ________
(Handle as a W/H, to F/N.)

33. WAS A QUESTION LEFT UNFLAT?                           ________
(Find out which one, indicate it and handle to F/N.)

34. WAS AN F/N OVERRUN?                                   ________
(Find out on what Sec Check question or overt chain
and rehab.)

35. WAS AN F/N MISSED?                                    ________
(Find out on what Sec Check question or overt chain
and rehab.)

36. DID SOMEONE DEMAND A W/H YOU DIDN'T HAVE?             ________
(Indicate it if so. 2WC E/S to F/N.)

37. HAD YOU TOLD ALL?                                     ________
(Indicate it if so. 2WC E/S to F/N.)

38. WAS AN OVERT PROTESTED?                               ________
(Get what it was and get in Protest button on it.
Fully clean up the overt to F/N.)

39. WAS THERE A WITHHOLD THAT KEPT COMING UP?             ________
(Get who wouldn't accept it or said it still read.
Indicate it was a false read. 2WC the concern to F/N.)

40. DID YOU HAVE TO GET THE SAME WITHHOLD OFF
    MORE THAN ONCE?                                       ________
(Handle as in #39.)

41. DID SOMEONE SAY YOU HAD A WITHHOLD WHEN YOU
    DIDN'T?                                               ________
(Indicate it, 2WC E/S to F/N. For auditors trained
to D/L, date to blow and locate to blow the first
instance of the pc being told he had that W/H when
he didn't.)

42. DID SOMEONE SAY OR SEEM TO INFER THAT
    SOMETHING READ WHEN IT DIDN'T?                        ________
(2WC E/S to F/N. For auditors trained to D/L,
date to blow and locate to blow the first instance
of the pc being told that.)

43. WAS THERE AN OVERT OR WITHHOLD THAT WASN'T
    ACCEPTED?                                             ________
(Get what. Get who wouldn't accept it. Get off
any protest and inval, and clean it up E/S to F/N.)

44. DID SOMEONE INVALIDATE YOU FOR GETTING OFF A
    WITHHOLD?                                             ________
(2WC E/S to F/N.)

45. DID SOMEONE PUNISH YOU FOR GETTING OFF A WITHHOLD?    ________
(2WC E/S to F/N.)

46. WAS THERE A FALSE ACCUSATION?                         ________
(2WC E/S to F/N.)

47. NOT YOUR OVERT?                                       ________
(Indicate it. If it doesn't F/N on indication,
take it E/S to F/N.)

48. WERE YOU NOT HONEST WITH THE AUDITOR?                 ________
(Handle as a missed withhold, E/S to F/N.)
 
49. DID YOU HAVE AN INTENTION TO MAKE OTHERS WRONG?       ________
(2WC E/S to F/N.)
(C/S to program the case for full service fac
handling and False Purpose Rundown.)

50. WAS THERE A COMPUTATION YOU USED TO MAKE YOURSELF
    RIGHT AND OTHERS WRONG?                               ________
(2WC E/S to F/N.)
(C/S to program for full service fac handling.)

51. FALSELY VILIFYING SOMEONE TO COVER UP AN EVIL
    PURPOSE?                                              ________
(Get it off as an overt E/S to F/N.)
(C/S to program the case for Truth Rundown.)

52. WAS THERE AN EVIL PURPOSE?                            ________
(2WC E/S to F/N.)
(C/S to program the case for False Purpose Rundown.)

53. WAS SOME BAD INTENTION NOT DISCOVERED?                ________
(2WC E/S to F/N.)
(C/S to program the case for False Purpose Rundown.)

54. WAS SOME HIDDEN EVIL IMPULSE NOT REVEALED?            ________
(2WC E/S to F/N.)
(C/S to program the case for False Purpose Rundown.)

55. WAS THERE SOME NONSURVIVAL CONSIDERATION YOU
    DIDN'T MENTION?                                       ________
(2WC E/S to F/N.)
(C/S to program the case for False Purpose Rundown.)

56. WERE YOU PRETENDING TO BE PTS TO AVOID TAKING
    RESPONSIBILITY FOR SOME OUT-ETHICS SITUATION?         ________
(Handle as a withhold to F/N. Pull any overts.)
(C/S to program the case for False Purpose Rundown.)

57. DID THE AUDITOR NOT HEAR OR ACKNOWLEDGE
    WHAT YOU SAID?                                        ________
(Indicate the BPC. Get what the auditor missed and
clean it up E/S to F/N.)

58. DID THE AUDITOR GET ANGRY AT YOU?                     ________
(If this happened, indicate it is illegal to do so.
2WC E/S to F/N. Clean up any ARC break to F/N.)
(C/S to program for a QUESTIONABLE AUDITING REPAIR
LIST, HCOB 11 July 82 I.)

59. WERE THERE AUDITOR'S CODE BREAKS?                     ________
(Get what. Indicate it was illegal and 2WC E/S to F/N.)
(C/S to program for a QUESTIONABLE AUDITING REPAIR
LIST, HCOB 11 July 82 I.)

60. WERE YOU AFRAID OF WHAT MIGHT HAPPEN?                 ________
(2WC E/S to F/N.)

61. WAS THERE AN INJUSTICE?                               ________
(2WC E/S to F/N.)

62. WAS THERE A BETRAYAL?                                 ________
(2WC E/S to F/N.)

63. WAS ANYTHING SUPPRESSED?                              ________
(Clean it up E/S to F/N.)

64. WAS ANYTHING INVALIDATED?                             ________
(Clean it up E/S to F/N.)

65. WAS ANYTHING FALSIFIED?                               ________
(Clean it up as a W/H E/S to F/N.)

66. WAS ANYTHING PROTESTED?                               ________
(2WC E/S to F/N.)

67. WAS THERE ANY EVALUATION?                             ________
(2WC E/S to F/N.)

68. WAS SOMETHING MISUNDERSTOOD?                          ________
(Clean it up, clearing any MU words each to F/N.)

69. WERE YOU TIRED OR HUNGRY?                             ________
(2WC E/S to F/N.)

70. HAD YOU RECENTLY TAKEN DRUGS?                         ________ 
                           MEDICINE?                      ________
                           ALCOHOL?                       ________
(2WC E/S to F/N. Note for C/S.)

71. WERE YOU BEING SEC CHECKED ON A WRONG AREA?           ________
(2WC to F/N, getting the area or subject pc feels
he should be sec checked on and noting these for
the C/S.)

72. WAS THERE SOMETHING ELSE WRONG?                       ________
(If so and it doesn't clean up on 2WC, GF M5
and handle.)

73. HAS THE UPSET BEEN HANDLED?                           ________
(2WC If so, indicate it to F/N.)


L. RON HUBBARD
Founder

Revision assisted by
LRH Technical Research
and Compilations

LRH:RTRC:rw.sep.ja



******************************************************************

25. HCOB   22 Aug. 1966       Floating Needles, Listing Processes


      HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

      HCO BULLETIN OF 22 AUGUST 1966

Remimeo
All Exec Hats
Qual Hats
Tech Hats
HCO Hats


    FLOATING NEEDLES, LISTING PROCESSES


In sessions where the process being run on a pc involves a 
listing question (including S&D), please note that after the 
listing question has been thoroughly cleared with the preclear 
and then given to the pc that the process IS being run.

Should it happen, then, that while the pc is actually listing off 
the question (and has not gone momentarily out of session), the 
needle floats, this is the flat point or end phenomenon of the 
process and the whole subject and all further steps of it are 
dropped at once.

Whatever charge was on the listing question has blown, either 
with or without the preclear being analytically aware of it.

To continue the process beyond this point is out-tech by the 
process being overrun and is also a violation of our basic fast 
flow system.

Please note that whether there is a second leg to the process or 
not, like fitting an item found off a list into a bracket of 
commands, has no bearing on the fact that the process is flat.

If the needle floats while the pc is in-session listing off a 
question, then there is no charge left on that question and there 
will be no item to fit into the second leg of the process.

The process has served its purpose.

With training as immaculately precise as it is and auditors' comm 
cycles becoming effortlessly superlative, the gradients of our 
technology are so fine that the results of each process on each 
level will be achieved faster and faster.

Sometimes the velocity of the processing is such that the end 
phenomenon will occur on the process without the preclear being 
aware of what has happened. Ending the process at this point then 
gives the preclear the chance to move into the velocity of the 
process.

Please then acknowledge the power of our technology and keep 
winning.


L. RON HUBBARD
Founder

LRH:lb-r.cden.gm



******************************************************************

26. HCOB    1 Aug. 1968       The Laws of Listing and Nulling


      HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

      HCO BULLETIN OF I AUGUST 1968

Remimeo

CLASS III, SOLO VI & VII, ACADEMY AND SHSBC
    REQUIRED REVIEWED FOR SOLO AND VII

      (Compiled from earlier HCOBs
      and tapes of the early 60s to
      give the exact stable data)


     THE LAWS OF LISTING AND NULLING

       (Star-rate. No attestations
     allowed, Clay and demos required)


The following laws are the ONLY important rules of listing and 
nulling. If an auditor doesn't know these, he will mess up pcs 
thoroughly and awfully. An auditor who doesn't know and can't 
apply these is not a Level III auditor.


                  LAWS

1. The definition of a complete list is a list which has only one 
reading item on list.

2. A TA rising means the list is being overlisted (too long).

3. A list can be underlisted in which case nothing can be found 
on nulling.

4. If after a session the TA is still high or goes up, a wrong 
item has been found.

5. If pc says it is a wrong item, it is a wrong item.

6. The question must be checked and must read as a question 
before it is listed. An item listed from a nonreading question 
will give you a "dead horse," (no item).

7. If the item is on the list and nothing read on nulling, the 
item is suppressed or invalidated.

8. On a suppressed list, it must be nulled with suppressed. "On 
______ has anything been suppressed."

9. On an item that is suppressed or invalidated, the read will 
transfer exactly from the item to the button and when the button 
is gotten in the item will again read.

10. An item from an overlisted list is often suppressed.

11. On occasion when you pass the item in nulling, all subsequent 
items will read to a point where everything on list will then 
read. In this case take the first which read on first nulling.

12. An underlisted and overlisted list will ARC break the pc and 
he may refuse to be audited until list is corrected, and may 
become furious with auditor and will remain so till it is 
corrected.

13. Listing and nulling or any auditing at all beyond an ARC 
break without handling the ARC break first, such as correcting 
the list or otherwise locating it, will put a pc into a "sad 
effect."

14. A pc whose attention is on something else won't list easily. 
(List and null only with the rudiments in on the pc.)

15. An auditor whose TRs are out has difficulty in listing and 
nulling and in finding items.

16. Listing and nulling errors in presence of Auditor's Code 
violations can unstabilize a pc.

17. The lack of a specific listing question or an incorrect 
nonstandard listing question which doesn't really call for item 
will give you more than one item reading on a list.

18. You cease listing and nulling actions when a floating needle 
appears.

19. Always give a pc his item and circle it plainly on the list.

20. Listing and nulling are highly precise auditing actions and 
if not done exactly by the laws may bring about a down tone and 
slow case gain, but if done correctly exactly by the laws and 
with good auditing in general will produce the highest gains 
attainable.

NOTE: There are no variations or exceptions to the above. (Does 
not alter VA Power procedure.)

A failure to know and apply this bulletin will result in the 
assignment of very low conditions as these laws, if not known or 
followed, can halt case gain.


L. RON HUBBARD
Founder

LRH:jp.js.cden.gm



******************************************************************

27. HCOB   19 Sept 1968       "Old lists..."


      HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

    HCO BULLETIN OF 19 SEPTEMBER 1968

Remimeo
L&N Checksheet
Class VIII


Old lists are NOT TO BE COPIED. They are to be corrected in their
original form but using a different colored pen to show what has
been done -- always date new uses of these lists also using the
same color pen as used for renulling or addition to them.

When listing you always note down F, BDs, SF, LF, etc., next to
the items. This is done AS YOU LIST.


L. RON HUBBARD
Founder

LRH:jp.nt.rd.gm



******************************************************************

28. HCOB    7 Oct. 1968       Assessment


      HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

      HCO BULLETIN OF 7 OCTOBER 1968

Class VIII
  (SH, ASHO)

                ASSESSMENT


Assessment means the locating on a prepared list, one item.

Listing and nulling means the pc lists.

The laws of listing and nulling apply only to LISTING and nulling. 
It IS auditing.

The actions of assessment do not apply to listing and nulling and 
never have.

Assessment is from a prepared list. It was done around 1960. It 
still is used. It has its own actions.

But as the prepared lists as in Prehav became bulky, I then 
developed a NEW action where the pc listed.

DO NOT apply the rules of assessment, as in the E-Meter book, to 
listing and nulling.

These are two different actions entirely.

The key is that a list for assessment is always from a list 
prepared by the auditor or from an HCOB as in "7 resistive cases."

S&Ds, Remedy Bs, etc., are LISTED by the pc and follow the LAWS of 
listing and nulling.

This is assessment, a list prepared by the C/S or auditor, not the 
pc.

To get a clue to what happened, the C/S prepares a list:

   Lions      X
   Big Game   /    X
   Cats       X
   Felines    /    X
   Tigers     X
   Bearers    X
   Trucks     X
   Elephants  X
   Killing    F   LFBD [Editor: this item is circled]
   Camping    X

Then the auditor nulls it to ONE item.

This is then prepchecked or done on an L1 as a subject.

When you list and null, the pc gives the list.

Who got shot?

   Me         X     X
   Joe        X     X
   Bearers    F     /    X
   Elephants  X     X
   Tigers     LFBD  F    X

The auditor nulls this (Xes and second action noted).

TWO items are now reading so the auditor EXTENDS the list--

        Ext

IND --> The White Hunter  F   LFBD [Editor: this item is circled]
        The Dog           X

And then the auditor renulls the WHOLE list (second X, etc.) and 
only one item stays in, which is a complete list. That is the 
item. It is given to pc.


L. RON HUBBARD
Founder

LRH:jp.ei.rd.gm



******************************************************************

29. HCOB   20 Sept 1978       An Instant F/N is a Read


      HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

    HCO BULLETIN OF 20 SEPTEMBER 1978

Remimeo

         AN INSTANT F/N IS A READ

   Refs:
   HCOB 2 Nov. 68R   CASE SUPERVISOR CLASS VIII
                     THE BASIC PROCESSES
   HCOB 20 Feb. 70   FLOATING NEEDLES AND END PHENOMENA


An instant F/N is an F/N which occurs instantly at the end of the 
major thought voiced by the auditor or at the end of the major 
thought voiced by the pc (when he originates items or tells what 
the command means).

It will most usually be seen as a LFBD / F/N or a LF / F/N.

So what does this mean, "An instant F/N is a read"?

A read means there's charge there to handle. It means there is 
force connected with that significance which is available to the pc 
to view and run. It means that item is real to the pc.

An F/N means something has keyed out.

Now, a key-out is what we are looking for on many processes which 
are run. It means "Stop. End of process, end of rud, end of 
action." So an instant F/N does not always mean you should take up 
that item.

To sort this out, you will have to understand the basic mechanics 
of key-out, key-in and erasure. It will then become clear why an 
F/N is a read and when it is taken up. To confuse this could really 
mess up a pc.

For example, on ruds, Prepcheck questions, protest, overrun, 
rehabs, to name a few, an instant F/N would not be taken up. The EP 
of charge keyed out has been attained.

But to ignore an instant F/N on Dianetic items and certain 
correction lists, etc., will leave the pc with bypassed charge and 
major areas of case unhandled. The key is "Is a handling required 
on the item or is an F/N the legitimate EP?"

You will also have to understand that we are talking about INSTANT 
F/Ns. An F/N which continues to F/N through an assessment means "No 
Charge."

An instant F/N on an item means charge has just keyed out on that 
item and that it can key back in again. There are actions, as in 
Dianetics, where a key-out is not what you are going for. You want 
the postulate off the basic incident of the chain, which indicates 
you have an erasure.

In Dianetics an instant F/N takes precedence over all other reads. 
This is because the pc, having just keyed out the charge on that 
item, will find it most real. It will be the most runnable item. An 
instantly F/Ning item is taken up first. LFBD, LF, F and sF follow 
in their usual order.

The use of this thing is mainly a C/S use. A C/S can look down a 
column of two-way comm or look down an L and N list and spot what 
F/Ned. If the C/S doesn't realize that this was the item, he can 
then take erroneously some LFBD item or F item out of the columns 
of two-way comm as the resulting item for that subject.

The use of an F/N as a read is almost entirely relegated to the 
next C/S except when used in Dianetics.

Example: A C/S is looking for the actual service facsimile in two-
way comm. (You usually L and N to find service facs but you may 
have an instance where you found one in two-way comm.) The pc 
mentions several and finally one F/Ns. The C/S knows at once it is 
the service fac.

Example: A two-way comm has operated as a list and the C/S is 
trying to reconstruct it. Unless he knows that an F/N is a read, he 
might overlook the actual item on that list which is the one which 
occurred immediately before the F/N. This is the item.

When used in the session itself, the auditor has to know that an 
F/N is a read in doing L and N. The item which F/Ned is of course 
the item.

In a Dianetic session it is not uncommon to find a brief F/N 
occurring on a list or a preassessment. In Dianetics we are not 
interested in key-outs. We are interested in chains and erasures. 
So the "hottest reading item" on the list is the one that gave an 
F/N. Usually it will be a BD F/N. If the Dianetic auditor does not 
know that an instant F/N is a read, he is likely to ignore the item 
that F/Ned.

In Dianetics, you will find that an F/N taken up again will 
immediately key in, but this is what the Dianetic auditor wants.

The Scientology auditor is usually handling other phenomena, and if 
he bypassed an F/N and kept on going, the TA would go up and he 
would have trouble.

So the use of this principle is a very touchy thing and has to be 
understood.

Of course, the first thing you have to know about is what an F/N 
looks like.

This tech fully understood and applied will mean the difference 
between a case being fully handled and "just doing better." 
Understand it and use it. You'll see the difference in your 
results.


L. RON HUBBARD
Founder

LRH:nc.mf.gm



******************************************************************

30. HCOB   22 Apr. 1980R      Assessment Drills [encore]

[FZBA Editor:
 This bulletin appears twice in the coursepack. Presumably this
 is because the Level 3 checksheet calls for this item to be
 studied at two different places on the checksheet.

 To save space we won't repeat the bulletin.]


******************************************************************

31. HCOB   20 Apr. 1972 II    Product Purpose and Why and W/C
                              Error Correction
                              C/S Series 78


      HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

      HCO BULLETIN OF 20 APRIL 1972
                Issue II
Remimeo

             C/S Series 78

      PRODUCT PURPOSE AND WHY AND
         W/C ERROR CORRECTION


Where untrained auditors are finding Whys for a Danger Formula, 
or post purposes or post products as called for in the Esto 
System, you will get a certain amount of error and case 
disturbance. Such upsets also come from Word Clearing by 
incompetent persons.

The C/S should look for these especially when such campaigns are 
in progress. He should suspect them as a possibility when a case 
bogs.

A C/S must be sure all such papers and worksheets get into pcs' 
folders.

A common repair action is to

1. Do an assessment for type of charge.

2. Handle the charge found by the assessment done.

3. Fly all the reading items found on such assessments by two-way 
comm or direct handling.

4. Suspect LISTING ERRORS on any Why or purpose or product found, 
even though no list exists, and reconstruct the list and L4B and 
handle it.

5. Handle Word Clearing of any type in or out of session with a 
Word Clearing Correction List done in session by an auditor.

6. When Word Clearing is too heavy on the pc or doesn't clean up, 
suspect he has been thrown into implants which are mostly words 
or the words in some engram. As implants are actually just 
engrams, handle it with an L3B.

                 LISTING

Any item found out of session or by a nonauditor is suspect of 
being a listing and nulling (L&N) error even though no list was 
made.

TODAY A CORRECT L&N ITEM MUST BLOWDOWN AND F/N.

So treat such items as you would list errors and try to 
reconstruct the list and either confirm the item or locate the 
real item (may have been invalidated and suppressed) or extend 
the list and get the real item.

The real item will BD F/N.

One can establish what the situation is with a post purpose, a 
Why or a product or any other such item by doing an L4B.

             SELF-AUDITING

The commonest reason for self-auditing is a wrong or unfound L&N 
item.

People can go around and self-list or self-audit trying to get at 
the right Why or product or purpose after an error has been made.

               REACTION

NOTHING PRODUCES AS MUCH CASE UPSET AS A WRONG LIST ITEM OR A 
WRONG LIST.

Even, rarely, a DIANETIC LIST can produce wrong list reactions. 
Ask the pc for his somatics and he blows up or goes into apathy. 
Or blows. Or attacks the auditor.

ALL of the more violent or bad reactions on the part of the pc 
come from out-lists.

Nothing else produces such a sharp deterioration in a case or 
even illness.

              OUT-LISTS

Therefore, when one gets a sharp change in a case (like lowered 
tone, violence, blows, "determination to go on in spite of the 
Supervisor," long notes from pcs, self C/Sing, etc., etc.), the 
C/S SUSPECTS AN OUT-LIST.

This outness can occur in regular sessions even when the item was 
said to BD F/N.

It can occur in "coffee shop" (out of session auditing of 
someone) or by Estos or poorly trained or untrained staff members 
or even in life.

                PTS

When such actions as finding items by nonauditors are done on PTS 
people, the situation can be bad, so one also suspects the person 
to be PTS to someone or something.

"PTS" does not communicate well in an assessment question so one 
says, "Someone or something is hostile to you" and "You are 
connected to someone or something that doesn't agree with 
Dianetics or Scientology."

              REPAIRS

The main things to know when doing such repairs are (a) that such 
situations as wrong lists or upset people can occur in an org 
where untrained people are also using meters and (b) THAT IT IS 
UP TO THE C/S TO SUSPECT, DETECT AND GET THEM HANDLED IN REGULAR 
SESSION.

Do not ignore the possible bad influence.

As the good outweighs the bad in such cases, it is not a correct 
answer to forbid such actions.

It is a correct answer to require all such actions and worksheets 
become part of the folder.

One can also persuade the D of T or Qual to gen in the people 
doing such actions.

And do not ignore the effect such actions can have on cases and 
do not neglect to include them in C/Ses before going on with the 
regular program.

They can all be repaired.


L. RON HUBBARD
Founder

LRH:nt.rd.gm



******************************************************************

32. HCOB   11 Apr. 1977       List Errors, Correction of


      HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

      HCO BULLETIN OF 11 APRIL 1977

Remimeo
Level III
Level IV
Snr Class IV
Snr SHSBC
Ex Dn
All Class IV
  Auditors

               LIST ERRORS
              CORRECTION OF


It has been found that the correction of lists, a very vital 
piece of tech, has been a source of confusion in the field as it 
apparently has never been written up in an issue. It really is 
simple if you know your laws of L&N.

            VERIFYING A LIST

The correct procedure for verifying/correcting past L&Ns is to 
check the items as to whether or not they are correct. Then do an 
L4BRA on each list where the item is found to be incorrect. You 
would have to orient the pc to the listing question and the item. 
You do not direct the question to see if it read. And don't just 
do an L4BRA and then not find the right item for the pc as part 
of the handling (unless the question proves to be uncharged or 
some such).

            NULLING A LIST

One nulls a list when he doesn't get a BD F/N item on listing. 
The laws of L&N strictly apply. An L4BRA would be used if the 
action bogs with still no item found. One would also null lists 
the pc made where no item had been found, such as a two-way comm 
which turned into a listing action with the pc giving off items 
or a list the pc somehow made while not on a meter. In these 
cases there is no item to verify with the pc as correct. Just 
cull the items into a list, work out with the pc what the 
question was if it's not already noted, and null the list.

         RECONSTRUCTING A LIST

Sometimes you just don't have the list and can't get it or it's 
an old Why Finding or PTS interview for which there are no 
worksheets. In this case you get from the pc what the question 
was and then get him to give you the items that were already on 
the list as the item probably was already on the list and you 
don't want the pc to get into newly listing the question in PT 
and then getting into an overlisting situation. Just get him to 
give you the items he had already put on the list and more often 
than not you will get a BD F/N item. If you don't get the item 
that way, then you can extend the list.

             SELF-LISTING

Watch it on these, as every random stray thought a person has 
about "why this or that" does not mean it's a self-list. But do 
look for it on a person who is manifesting the horrendous BPC an 
out-list can generate, who is introspected or has been trying to 
figure out who is doing him in after just having seen the Ethics 
Officer. Just don't get into trying to make a list out of some 
nonstandard listing question that won't give you an item. And 
actually, the usual reason for self-listing is a prior wrong L&N 
item or an item not found. People will self-list to try to find 
the right item. So find and correct the earlier out-list.

         LIST CORRECTION BLOWUP

When you are going along correcting lists and suddenly you get a 
big pc blowup and it is not resolving on the list you are 
correcting, you had better quickly realize that you probably are 
not correcting the list that is out and you'd better find out 
which list it is. There is usually an earlier out-list to be 
found, if the list you are correcting does not resolve the upset.

          LISTS NOT READING

When you start getting key lists, such as Grades III and IV, not 
reading and no items found, it's time for that auditor to get a 
thorough overhaul on his metering, eyesight and to get off all 
his MUs on L&N. You also could be setting the pc up for a self-
listing situation, as he has been given the listing question but 
no item has been found. So be very sure the question did not read 
even with Suppress and Inval and TRs were in before getting off a 
key L&N process.

            USE OF L4BRA

The prepared list L4BRA corrects L&N lists. It can be run on old 
lists, current lists, general listing. When a pc is ill after a 
listing and nulling session or up to three days after, always 
suspect that a listing action done on the pc had an error in it 
and get those lists corrected.

Sometimes it is obvious what the error was per the laws of 
listing and nulling. For example, there could be two reading 
items left on the list in which case you would know to extend the 
list as it has been underlisted. If this didn't go, then an L4BRA 
would be done on the list.

         HANDLING AN L4BRA

You handle reading questions on the L4BRA by the directions under 
the question that read. You don't just two-way comm these 
questions. For example, say question 4 read on the L4BRA. "Is a 
list incomplete? SF." You then ask the pc, "What list is 
incomplete?" Locate it and get it completed to a BD F/N item. You 
don't just two-way comm "incomplete lists" to an F/N and leave it 
at that.

By the way, the L4BRA is missing a line which is "Was it the 
first item on the list?" This is being added as it's quite common 
that it is the first item and is most often missed.

           DO IT RIGHT

An out-list can create more concentrated hell with a pc than any 
other single auditing error. So it's imperative that listing 
errors get properly corrected.

The best thing to do is to have the laws of listing and nulling 
drilled line by line and down cold and just do it right in the 
first place. Then you will also see at once where old lists 
violated these laws and you will not be yourself doing lists that 
have to be corrected later.


L. RON HUBBARD
Founder

Assisted by CS-4/5

LRH:JE:dr.gm



******************************************************************

33. HCOB   15 Dec. 68RA       L4BRA, For Assessment of All Listing
                              Errors


      HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

    HCO BULLETIN OF 15 DECEMBER 1968RA
         RE-REVISED 11 APRIL 1977

Remimeo

                   L4BRA
    FOR ASSESSMENT OF ALL LISTING ERRORS


ASSESS THE WHOLE LIST (METHOD 5) THEN TAKE biggest reads or 
blowdowns and handle. Then clean up the list.


PC'S NAME________________________________ DATE____________________

AUDITOR _________________________________


0. WAS IT THE FIRST ITEM ON THE LIST?                    ________
   (Indicate and give pc his item.)

1. DID YOU FAIL TO ANSWER THE LISTING QUESTION?          ________
   (If it reads, find out what question, clear the
   question noting whether it reads, if so, list it,
   find the item and give it to the pc.)

2. WAS THE LIST UNNECESSARY?                             ________
   (If it reads, indicate BPC and indicate that it
   was an unnecessary action.)

2A. DID THE QUESTION HAVE NO CHARGE ON IT?               ________
    (Indicate.)

2B. WERE YOU ASHAMED TO CAUSE AN UPSET?                  ________
    (L1C after list corrected.)

2C. WERE YOU AMAZED TO REACT THAT WAY?                   ________
    (Same as 2B.)

2D. THE QUESTION HAD ALREADY BEEN LISTED BEFORE?         ________
    (Indicate, rehab.)

2E. YOU HAD NO INTEREST IN THE QUESTION?                 ________
    (Indicate that the auditor missed that it
    didn't read.)

3. WAS THE ACTION DONE UNDER PROTEST?                    ________
   (If it reads, handle by itsa earlier-similar
   itsa.)

4. IS A LIST INCOMPLETE?                                 ________
   (If reads, find out what list and complete it,
   give the pc his item.)

5. HAS A LIST BEEN LISTED TOO LONG?                      ________
   (If so, find what list and get the item from it by
   nulling  with Suppress, the nulling question being
   "On ______ has anything been suppressed?" for each
   item on the overlong list. Give the pc his item.)

6. HAS THE WRONG ITEM BEEN TAKEN OFF A LIST?             ________
   (If this reads, put in Suppress and Invalidate on
   the list and null as in 5 above and find the right
   item and give to the pc.)

7. HAS A RIGHT ITEM BEEN DENIED YOU?                     ________
   (If this reads, find out what it was and
   clean it up with Suppress and Invalidate and
   give it to the pc.)

8. HAS AN ITEM BEEN PUSHED OFF ON YOU YOU
   DIDN'T WANT?                                          ________ 
   (If so, find it and get in Suppress and
   Invalidate on it and tell pc it wasn't his
   item and continue the original action to
   find the correct item.)

9. HAD AN ITEM NOT BEEN GIVEN YOU?                       ________
   (If reads, handle as in 7.)

10. HAVE YOU INVALIDATED A CORRECT ITEM FOUND?           ________
    (If so, rehab the item and find out why the pc
    invalidated it or if somebody else did it,
    clean it up and give it to pc again.)

11. HAVE YOU THOUGHT OF ITEMS THAT YOU DID NOT
    PUT ON THE LIST?                                     ________
    (If so, add them to the correct list. Renull
    the whole list and give the pc the item.)

12. HAVE YOU BEEN LISTING TO YOURSELF OUT OF SESSION?    ________
    (If so, find out what question and try to write a
    list from recall and get an item and give it to
    the pc.)

13. HAVE YOU BEEN GIVEN SOMEBODY ELSE'S ITEM?            ________
    (If so, indicate to the pc this was not his
    item. Don't try to find whose it was.)

14. HAS YOUR ITEM BEEN GIVEN TO SOMEONE ELSE?            ________
    (If so, find if possible what item it was
    and give it to the pc. Don't try to identify
    the "somebody else.")

14A. WERE EARLIER LISTING ERRORS RESTIMULATED?           ________
     (Indicate and correct earlier lists then
     check the current.)

14B. HAD THIS LIST ALREADY BEEN HANDLED?                 ________
     (Indicate.)

15. HAS A RELEASE POINT BEEN BYPASSED ON LISTING?        ________
    (If so, indicate the overrun to the pc,
    rehab back.)

16. HAS A RELEASE POINT BEEN BYPASSED ON THE
    QUESTION ONLY?                                       ________
    (If so, indicate the overrun to the pc and
    rehab back.)

17. HAVE YOU GONE EXTERIOR WHILE LISTING?                ________
    (If so, rehab. If Ext Rundown not given,
    note for C/S.)

18. HAS IT BEEN AN OVERT TO PUT AN ITEM ON A LIST?       ________
    (If so, find out what item and why.)

19. HAVE YOU WITHHELD AN ITEM FROM A LIST?               ________
    (If so, get it and add it to the list if
    that list available. If not, put item in
    the report.)

20. HAS A WITHHOLD BEEN MISSED?                          ________
    (If so, get it; if discreditable ask "Who nearly
    found out?")

21. HAS AN ITEM BEEN BYPASSED?                           ________
    (Locate which one.)

22. WAS A LISTING QUESTION MEANINGLESS?                  ________
    (If so, find out which one and indicate
    to the pc.)

23. HAS AN ITEM BEEN ABANDONED?                          ________
    (If so, locate it and get it back for the pc and
    give it to him.)

24. HAS AN ITEM BEEN PROTESTED?                          ________
    (If so, locate it and get the Protest button
    in on it.)

25. HAS AN ITEM BEEN ASSERTED?                           ________
    (if so, locate it and get in the Assert
    button on it.)

26. HAS AN ITEM BEEN SUGGESTED TO YOU BY ANOTHER?        ________
    (If so, get it named and the protest and
    refusal off.)

27. HAS AN ITEM BEEN VOLUNTEERED BY YOU AND NOT
    ACCEPTED?                                            ________
    (If so, get off the charge and give it to the
    pc, or if he then changes his mind on it, go
    on with the listing operation.)

28. HAS THE ITEM ALREADY BEEN GIVEN?                     ________
    (If so, get it back and give it again.)

29. HAS AN ITEM BEEN FOUND PREVIOUSLY?                   ________
    (If so, find what it was again and give it
    to the pc once more.)

30. HAS AN ITEM NOT BEEN UNDERSTOOD?                     ________
    (If so, work it over with buttons until pc
    understands it or accepts or rejects it and
    go on with listing.)

30A. WAS THE LISTING QUESTION NOT UNDERSTOOD?            ________
     (Get defined and check for read. It may be
     unreading. If so, indicate that an uncharged
     question was listed because it read on a
     misunderstood.)

30B. WAS A WORD IN THE QUESTION NOT UNDERSTOOD?          ________
     (Same as 30A.)

31. WAS AN ITEM DIFFERENT WHEN SAID BY THE
    AUDITOR?                                             ________
    (If so, find out what the item was and give it
    to the pc correctly.)

31A. DID THE AUDITOR SUGGEST ITEMS TO YOU THAT
     WERE NOT YOURS?                                     ________
     (Indicate as illegal to do so. Correct the list,
     removing these.)

32. WAS NULLING CARRIED ON PAST THE FOUND ITEM?          ________
    (If so, go back to it and get in Suppress and
    Protest.)

33. HAS AN ITEM BEEN FORCED ON YOU?                      ________
    (If so, get off the reject and suppress and get
    the listing action completed to the right item
    if possible.)

34. HAS AN ITEM BEEN EVALUATED?                          ________
    (If so, get off the disagreement and protest.)

35. HAD EARLIER LISTING BEEN RESTIMULATED?               ________
    (If so, locate when and indicate the bypassed
    charge. Find and correct the earlier out-list.)

36. HAS AN EARLIER WRONG ITEM BEEN
    RESTIMULATED?                                        ________
    (If so, find when and indicate the bypassed
    charge. Find and correct the earlier out-list.)

37. HAS AN EARLIER ARC BREAK BEEN RESTIMULATED?          ________
    (If so, locate and indicate the fact by itsa
    earlier-similar itsa.)

38. DO YOU HAVE AN ARC BREAK BECAUSE OF BEING
    MADE TO DO THIS?                                     ________
    (If so, indicate it to the pc. Handle the
    ARC break. Correct the list if it's a list
    ARC break.)

39. HAS THE LIST CORRECTION BEEN OVERRUN?                ________
    (If so, rehab.)

39A. WAS THE LIST DONE WHILE YOU ALREADY HAD AN
     ARC BREAK, PTP OR W/H?                              ________

39B. COULDN'T YOU UNDERSTAND WHAT WAS BEING DONE?        ________

39C. COULDN'T YOU UNDERSTAND THE AUDITOR?                ________

39D. DIDN'T THE AUDITOR ACKNOWLEDGE YOU?                 ________

40. IS THERE SOME OTHER KIND OF BYPASSED CHARGE?         ________
    (If so, find what and indicate it to pc.)

41. WAS THERE NOTHING WRONG IN THE FIRST PLACE?          ________
    (If so, indicate it to pc.)

42. HAS THE UPSET BEEN HANDLED?                          ________
    (If so, indicate it to the pc.)

43. HAS A LIST PROCESS BEEN OVERRUN?                     ________
    (If so, find which one and rehab.)


L. RON HUBBARD
Founder

Assisted by CS-4/5

LRH:JE:Idm.rw.dz.rr.nt.dr.kjm.gm



******************************************************************

34. HCOB    6 Aug. 1968       R3H


       HUBBARD COMMUNICATIONS OFFICE
 Saint Hill Manor, East Grinstead, Sussex

       HCO BULLETIN OF 6 AUGUST 1968

Remimeo

                LEVEL III
          IMPORTANT--STAR-RATED

                   R3H

     (Takes precedence over all other
            HCOBs and tapes)


The way to handle the ARC breaks of a case with R3H as the 
process for Level III is

1. Locate a change in life by listing to a blowdown. Use that 
period. "What change has happened in your life" is a version of 
the question.

2. Get it dated.

3. Get some of the data of it (don't run as an engram) so you 
know what the change was.

4. Find out by assessment if this was a break in

     Affinity
     Reality
     Communication or
     Understanding

   and have the pc examine that briefly.

5. Taking the one found in (4), find out by assessment if it was

     Curious about _________
     Desired _______________
     Enforced ______________
     Inhibited _____________

That is all there is to it.

That was the research process.

It works like a bomb.

To make sure it works well, get in the rudiments before you do 
it.

               ----------

It has been said that you can do this several times on a pc 
beyond a floating needle on one. I have not verified this.

               ----------

Doing Know-Unknown-Curious, etc., first is definitely wrong. ARC 
is dominant. ARC is done first as above. Understanding is the 
composite of ARC and so is added to ARC as U in (4) above.


L. RON HUBBARD
Founder

LRH:jp.js.cden.gm






